Generic small features
Public.icon
Sometimes it's better to have the freedom to combine small generic features rather than using a specialized UI for a specific task.
First, throw away GitHub Issue, and then create a network of requests and demands on Scrapbox to think carefully about what you can do. Gyazo also says pretty much the same thing. Gyazo's philosophy, I couldn't agree more.
・Keep it simple
・Issue driven
・Don't listen to opinions
— Yamotty | Masajo Yamamoto (10X) (@yamotty3) May 8, 2018 yamotty3 of 10X, who is developing Stailer., is very conscious of abstraction and generalization. The flow of doing logistics for net supermarkets with Stailer. itself, which resulted from doing consumer products, is the concept of Vertical markets. As a countermeasure (?), /shokai seems to be trying to maximize the resolution of Geeks and Suits, as repeatedly mentioned. Even though I get a lot of feedback on the app's UI from various people, I'm mostly focused on selecting the most generic and simple solution from an infinite number of possible solutions for unresolved issues.
It's often the case that the priority of measures is determined by impact and man-hours, but in the case of 10X, it seems to be judged by the depth and breadth (discontinuity) of the issue and uncertainty. And qualitative and quantitative analysis to support it, development power, cash, and issue resolution resolution. --Please tell us why you decided to provide it as a general-purpose product rather than accepting the development of a net supermarket for one company.
/emoji/twitter.icon After learning that it took snap a year to come up with an innovative answer called the story function in response to a user's request for a group message function, I started to question whether it was easy to add functions. https://t.co/RLtX2z8qqS